home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-20
/
nosvw.zip
/
RIP
< prev
next >
Wrap
Text File
|
1991-09-18
|
6KB
|
146 lines
=== NOSview [137]
rip
===
_________________________________________________________________
rip accept <incoming_gateway_host>
_________________________________________________________________
Remove the specified gateway from the RIP filter table, allowing
future broadcasts from that gateway to be accepted.
>> Example: rip accept ns9liz
_________________________________________________________________
rip add <destination_host> <seconds> [<flags>]
_________________________________________________________________
Add an entry to the RIP broadcast table. The IP routing table
will be sent to <destination_host> at <seconds> intervals.
Flags settings:
1: include route to self
2: split horizon
4: triggered update
If flags is specified as 1, then "split horizon" processing will
be performed for this destination. That is, any IP routing table
entries pointing to the interface that will be used to send this
update will be removed from the update. If split horizon
processing is not specified, then all routing table entries
except those marked "private" will be sent in each update.
(Private entries are never sent in RIP packets).
Triggered updates are always done. That is, any change in the
routing table that causes a previously reachable destination to
become unreachable will trigger an update that advertises the
destination with metric 15, defined to mean "infinity".
Note that for RIP packets to be sent properly to a broadcast
address, there must exist correct IP routing and ARP table
entries that will first steer the broadcast to the correct
interface and then place the correct link-level broadcast address
(callsign) in the link-level destination field.
If a standard IP broadcast address convention is used (e.g.
128.96.0.0 or 128.96.255.255) then chances are you already have
the necessary IP routing table entry, but unusual subnet or
cluster-addressed networks may require special attention.
However, an 'arp add' command will be required to translate this
address to the appropriate link level broadcast address.
For example, for an AX.25 packet radio channel:
arp add 44.255.255.255 ax25 qst-0
and for an Ethernet network:
arp add 128.96.0.0 ethernet ff:ff:ff:ff:ff:ff
>> Example: rip add uk 900 6
_________________________________________________________________
rip drop <destination_host>
_________________________________________________________________
Remove an entry from the RIP broadcast table.
>> Example: rip drop ns9liz
_________________________________________________________________
rip merge [on | off] Default: on
_________________________________________________________________
This flag controls an experimental feature for consolidating
redundant entries in the IP routing table.
When rip merging is on, the table is scanned after processing
each RIP update. An entry is considered redundant if the
target(s) it covers would be routed identically by a less
"specific" entry already in the table. That is, the target
address(es) specified by the entry in question must also match
the target addresses of the less specific entry and the two
entries must have the same interface and gateway fields.
For example, if the routing table contains
Dest Len Interface Gateway Metric P Timer Use
1.2.3.4 32 ethernet0 128.96.1.2 1 0 0 0
1.2.3 24 ethernet0 128.96.1.2 1 0 0 0
then the first entry would be deleted as redundant since packets
sent to 1.2.3.4 will still be routed correctly by the second
entry. Note that the relative metrics of the entries are
ignored.
>> Example: rip merge off
_________________________________________________________________
rip refuse <incoming_gateway_host>
_________________________________________________________________
Refuse to accept RIP updates from the specified gateway by adding
the gateway to the RIP filter table. It may be later removed
with the 'rip accept' command.
>> Example: rip refuse ns9liz
_________________________________________________________________
rip request <incoming_gateway_host>
_________________________________________________________________
Send a RIP Request packet to the specified gateway, causing it to
reply with a RIP Response packet containing its routing table.
>> Example: rip request ns9liz
_________________________________________________________________
rip status
_________________________________________________________________
Display RIP status, including a count of the number of packets
sent and received, the number of requests and responses, the
number of unknown RIP packet types, and the number of refused RIP
updates from hosts in the filter table.
A list of the addresses and intervals to which periodic RIP
updates are being sent is also shown, along with the contents of
the filter table.
_________________________________________________________________
rip trace [0 | 1 | 2] Default: 0
_________________________________________________________________
This variable controls the tracing of incoming and outgoing RIP
packets.
Setting it to 0 disables all RIP tracing.
A value of 1 causes changes in the routing table to be displayed,
while packets that cause no changes cause no output.
Setting the variable to 2 produces maximum output, including
tracing of RIP packets that cause no change in the routing table.
>> Example: rip trace 2